Systems and methods for monitoring credit of trading counterparties

ABSTRACT

Systems and methods are provided which monitor trades entered into and cleared by counterparties, track the net and gross positions of counterparties and the counterparties&#39; parent entities, trigger warnings when counterparties or their parent entities exceed a warning limit, and shut-off counterparties&#39; trading ability when counterparties exceed a credit limit. An operator of a credit system using these systems and methods is provided with a variety of interfaces through which the operator can set up new counterparties, search a list of counterparties, view and edit basic information for counterparties, view financial information for counterparties, view and edit notes regarding to counterparties, view and edit limits of counterparties, view position versus limit information for counterparties, view the current day&#39;s position information for counterparties, and view cumulative position information for counterparties.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication No. 60/174/896, filed Jan. 6, 2000, which is herebyincorporated by reference herein in its entirety.

BACKGROUND OF THE INVENTION

The present invention relates to systems and methods for monitoringcredit of trading counterparties. More particularly, the presentinvention relates to systems and methods for monitoring credit oftrading counterparties that enable trading systems and credit managersto monitor credit of trading counterparties and thereby control the riskthat the trading system and the trading counterparties are exposed to.

In recent years, electronic trading systems have gained wide spreadacceptance for trading of a wide variety of items, such as goods,services, financial instruments, and commodities. For example,electronic trading systems have been created which facilitate thetrading of financial instruments and commodities such as stocks, bonds,currency, futures, oil, gold, pork bellies, etc. As another example,online auctions on the Internet have become popular markets for theexchange of services and both new and used goods.

Trading systems are frequently operated by individual traders in orderto effect trades for legal entities with which they are employed. Forexample, a bank may employ various traders who participate in trading inthe bond market. In trading system, both the traders and the banks mayeach maintain a trading account, and thus each is a counterparty in thetrading systems. Similarly, a holding company may own several banks, andeach bank may employ several traders. As above, the holding company mayalso maintain a trading account, and thus the holding company is also acounterparty in the trading system. The accounts that are held mayfollow the same type of structural hierarchy. For example, the holdingcompany may have a trading account, each bank may have a sub-account ofthe holding company's account, and each trader may have a sub-account oftheir bank's account. In the context of this invention, a customer of atrading system may be any person or entity holding one or more tradingaccounts and may be also referred to as a counterparty. For example, theholding company may hold its own account as well as the accounts of itsbanks, and each bank may hold its own account as well as the accounts ofits traders. Also in the context of this invention, the holding companyis the parent entity of the banks and the banks are the parent entitiesof their traders.

Many of these electronic trading systems use a bid/offer process inwhich bids and offers are submitted to the systems by a passive side andthen those bids and offers are hit and lifted (or taken) by anaggressive side. For example, a passive trading counterparty may submita “bid” to buy a particular number of 30 Year U.S. Treasury bonds at agiven price. In response to such a bid, an aggressive side counterpartymay submit a “hit” in order to indicate a willingness to sell bonds tothe first counterparty at the given price. Alternatively, a passive sidecounterparty may submit an “offer” to sell the particular number of thebonds at the given price, and then an aggressive side counterparty maysubmit a “lift” (or “take”) in response to the offer to indicate awillingness to buy bonds from the passive side counterparty at the givenprice.

When trades are entered into by one counterparty submitting a bid oroffer and another counterparty hitting or lifting the bid or offer,respectively, a binding contract between the counterparties is enteredinto. Part of that contract requires that the counterparties eachdeliver money, goods, and/or services. For example, if a firstcounterparty bids to buy $100 million in 30 year U.S.

Treasury bonds, and a second counterparty hits the bid, the firstcounterparty has to deliver $100 million in cash and the secondcounterparty has to deliver the 30 year U.S. Treasury bonds within apredetermined clearing time. This process is referred to as a tradeclearing.

Because counterparties have the potential to lose money when trades donot clear because of subsequent changes in market conditions,counterparties frequently desire to, and are frequently required bytheir parent entities to, limit their risk exposure. One way in whichrisk exposure can be limited is to place a monetary limit on the amountof trades that can be made in one day. This limit is referred to as acredit limit. The monetary total amount of trades that may be made isreferred to as the credit available to the counterparty, and themonetary total amount of trades that have been entered into so far isreferred to as the position of the counterparty.

Accordingly, it is an object of the present invention to provide systemsand methods for monitoring credit of trading counterparties.

SUMMARY OF THE INVENTION

In accordance with this and other objects of the invention, systems andmethods for monitoring credit of trading counterparties are provided.More particularly, the present invention is systems and methods formonitoring credit of trading counterparties that enable trading systemsand credit managers to monitor credit of trading counterparties andthereby control the risk that the trading system and the tradingparticipant are exposed to. In one aspect of the present invention, thesystems and methods monitor trades entered into and cleared bycounterparties, track the net and gross positions of counterparties andthe counterparties' parent entities, trigger warnings whencounterparties or their parent entities exceed a warning limit, andshut-off counterparties' trading ability when counterparties exceed acredit limit. In another aspect of the present invention, an operator ofa credit system is provided with a variety of interfaces through whichthe operator can set up new counterparties, search a list ofcounterparties, view and edit basic information for counterparties, viewfinancial information for counterparties, view and edit notes regardingcounterparties, view and edit limits of counterparties, view positionversus limit information for counterparties, view the current day'sposition information for counterparties, and view cumulative positioninformation for counterparties.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features of the invention, its nature and various advantageswill become more apparent from the following detailed description of theinvention, taken in conjunction with the accompanying drawings, in whichlike reference characters refer to like parts throughout, and in which:

FIG. 1 is a block diagram of hardware that may be used to implementvarious embodiments of the present invention;

FIG. 2 is a flow diagram of a credit monitoring process in accordancewith various embodiments of the present invention;

FIG. 3 is an illustration of a main menu that may be presented inaccordance with various embodiments of the present invention; and

FIGS. 4-21 are illustrations of various credit processor operatorinterfaces that may be presented in accordance with various embodimentsof the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention is now described in connection with FIGS. 1-21.Turning first to FIG. 1, an example of hardware 100 that may be used toimplement one embodiment of the present invention is shown. Asillustrated, hardware 100 may include one or more local workstations 102and one or more remote workstations 104 that may be used bycounterparties to view trading data and enter trading commands.Workstations 102 and 104 may be any suitable means for presenting dataand, in preferred embodiments of this invention, accepting input. Forexample, workstations 102 and 104 may be personal computers, laptopcomputers, mainframe computers, dumb terminals, data displays, Internetbrowsers, Personal Digital Assistants (PDAs), two-way pagers, wirelessterminals, portable telephones, etc., or any combination of the same.

To orchestrate trading between counterparties using workstations 102 and104, the workstations preferably submit commands to, and receive data tobe displayed from, a processor 106. In alternative embodiments, however,workstations may communicate with additional processors, or includeprocessors to orchestrate trading in a distributed fashion withoutrequiring processor 106. In yet other embodiments, processor 106 may beconnected to an external trading system (not shown) that controlstrading by the counterparties. Processor 106, and any additionalprocessors, may be any suitable circuitry or devices capable ofprocessing data such as microprocessors, personal computers, networkservers, mainframe computers, dedicated computer systems, etc.

As shown, processor 106 may be connected to workstations 102 and 104 bynetworks 108 and 110, respectively. Each of networks 108 and 110 may beany suitable data network for communicating data between workstations102 and 104 and processor 106, such as a local area network, a wide areanetwork, the Internet, an intranet, a wireless network, a hard wiredconnection, a dial-up network, etc., or any combination of the same. Inan arrangement of hardware 100 without processor 106, workstations 102and 104 may be linked together by networks 108 and 110 directly.

Workstations 102 and 104, processor 106, and networks 108 and 110 maycollectively form a trading system.

As also shown in FIG. 1, a telephone network 126 may be provided thatcomprises a local telephone 128 and a remote telephone 130 connected bya telephone line 132. Telephone network 126 may be used to enable acounterparty at a remote location to communicate with abroker-counterparty at a workstation 102 or 104. This may be useful whenthe counterparty does not have access to a workstation 102 or 104 orwhen the counterparty only has access to a display-only workstation 102or 104. Obviously, telephone network 126 may be implemented as a privatetelephone network, a public telephone network, a wireless telephonenetwork, or any suitable combination of the same.

When used to implement a bid/offer, hit/take trading system as describedabove or connect to an external bid/offer, hit/take trading system,hardware 100 may enable a counterparty to submit a bid to buy, or anoffer to sell, an item at one of workstations 102 and 104. This bid oroffer may then be communicated to processor 106, where the bid or offercan be ranked and stored in a bid-offer queue. The ranking may be basedupon time of submission, price, or any other suitable criterion. The bidor offer may then be presented to other counterparty via otherworkstations 102 and 104 dependent upon its ranking in the bid-offerqueue. Once displayed, the bid or offer can then be hit or taken by oneor more of the other counterparty so that a trade of the item canproceed to execution.

A back office clearing system 112 and a credit processor 114 may also beconnected to processor 106 of the trading system via communication links118 and 120, respectively. Clearing system 112 may be any suitableequipment, such as a computer, or combination of the same, for causingtrades to be cleared and/or verifying that trades are cleared. Creditprocessor 114 may be any suitable equipment, such as a computer, orcombination of the same, for monitoring and controlling credit asdescribed hereinbelow. Credit processor 116 may be controlled by one ormore operator terminals 116 via communication link 124, and/or byworkstations 102 and 104 via networks 108 and 110 and processor 106.Operator terminals 116 may be any suitable circuitry or devices capableof providing a control interface for credit processor 114 such asmicroprocessors, personal computers, network servers, mainframecomputers, dedicated computer systems, dumb terminals, computer monitorand keyboard, etc. Clearing system 112 may communicate with creditprocessor 114 via communication link 122, and communication links 118,120, 122, and 124 may be any suitable data network for communicatingdata, such as a local area network, a wide area network, the Internet,an intranet, a wireless network, a hard wired connection, a dial-upnetwork, etc., or any combination of the same.

Turning to FIG. 2, an example of a process 200 that may be executed incredit processor 114 is illustrated. As shown, at steps 202 and 204,trade information may be received from processor 106 of the tradingsystem and back office clearing system 112. The trade information fromprocessor 106 may include the price, size, and item to be traded inconnection with trades entered into by each counterparty. The tradeinformation from clearing system 112 may include price, size, and itemthat was supposed to be traded in connection with trades that cleared orfailed to clear for each counterparty. The trading information may bereceived at credit processor 114 as soon as the information is availableor may be periodically received in batches.

After receiving trade information from processor 106 at step 202,process 200 may calculate the long-bond-equivalent for each trade basedupon the size (e.g., quantity) and type (e.g., security and maturity) ofthe item to be traded at step 206. The long-bond-equivalent (LBE) is ametric that is used to convert that values of various types of trades toa uniform scale and is based on the value of a long bond (i.e., a 30year U.S. Treasury Bond). Although long-bond-equivalents are used toillustrate the invention, any suitable metric may be used to implementthe invention. Next, at step 208, process 200 may accumulate the LBEshort and long positions for each counterparty account corresponding tothe received information. A long position is a position wherein acounterparty agrees to buy an item and a short position is a positionwherein a counterparty agrees to sell an item. Next at step 210, process200 may accumulate the LBE short and long positions for all accounts ofeach parent entity having counterparties corresponding to the receivedinformation.

After receiving trade information from clearing system 112 at step 204,process 200 may re-calculate the long-bond-equivalent for each tradebased upon the size (e.g., quantity) and type (e.g., security andmaturity) of the item traded at step 212, if necessary. Next, at step214, process 200 may adjust the LBE short and long positions for eachcounterparty account corresponding to the received information, ifnecessary. Where a trade has cleared, for example, the counterpartyaccount may be deducted by the amount of the trade to reflect that thetrade is no longer “on credit.” Next at step 216, process 200 may adjustthe LBE short and long positions for all accounts of each parent entityhaving counterparties corresponding to the received information, ifnecessary.

Upon completing step 210 or step 216, process 200 may next determine atstep 218 whether the counterparty accounts corresponding to theinformation have credit limits. For each account having a credit limit,process 200 may next check the account position against its accountlimit at step 220. The account's position is preferably the valueaccumulated at steps 208 and 214. Next, at step 222, process 200determines if the account's position is within the warning level rangefor the account. The warning level range is a range in which acounterparty, credit manager, trading system administrator, or anyone oranything else may be warned that the account is approaching its limit.If the account's position is not within the warning level range, thenprocess 200 determines if the account's position is over its creditlimit at step 224. If the account's position is not over its creditlimit, then process 200 proceeds to step 226 to wait for moreinformation from processor 106 or clearing system 112. Otherwise, if theaccount position is over its credit limit, process 200 may shut off theaccount at step 228. Finally, after shutting off the account at step228, or if the account is determined to be within the warning levelrange at step 222, process 200 may send a message, at step 230, to oneor more pagers of designated persons with information relating to theaccount, such as account number, position, and limit, and then wait formore trade information at step 226.

If process 200 determines at step 218 that the account does not have acredit limit, however, then process 200 proceeds to step 232 where itdetermines whether the parent entity having the counterpartycorresponding to the account has a credit limit. This limit wouldencompass an account limit for the account if one existed. If process200 determines at step 232 that the parent entity does not have a creditlimit, then process 200 may shut off the parent entity and all of itscounterparties by disabling their trading accounts at step 234. Aftershutting off these accounts at step 234, process 200 may send a message,at step 230, to one or more pagers of designated persons withinformation relating to the accounts, such as account numbers,positions, and limits, and then wait for more trade information at step226.

If process 200 determines at step 232 that the parent entity does have acredit limit, however, process 200 may then check the parent entity'sposition against its credit limit at step 236. The parent entity'sposition is preferably the value accumulated at steps 210 and 216. Next,at step 238, process 200 may determine whether the parent entity'sposition is within the warning level range for that entity. If theparent entity's position is within the warning level range, then process200 may send a message, at step 240, to one or more pagers of designatedpersons with information relating to the parent entity, such ascounterparty number, position, and limit, and then wait for more tradeinformation at step 226.

If process 200 determines at step 238 that the parent entity's positionis not within the warning level range, then process 200 may determine atstep 242 whether the parent entity's position is over the parententity's credit limit. If the parent entity's position is over itscredit limit, then process 200 may shut off the parent entity and all ofits counterparties by disabling their trading accounts at step 234 andsend a message to one or more pagers of designated persons withinformation relating to the accounts, such as account numbers,positions, and limits, at step 230. After sending a message at step 230,of if process 200 determines at step 242 that the parent entity'sposition is not over its credit limit, process 200 may wait for moretrade information at step 226.

Turning to FIGS. 3-21, examples of user interfaces that may be presentedto an operator of credit processor 114 via operator terminal 116 and/orworkstations 102 and/or 104 are illustrated. As shown in FIG. 3, a mainmenu 300 is illustrated. Main menu 300 is illustrated with icons 301-311which are supplemented by text, although main menu may be implemented inany suitable manner. Main menu 300 allows an operator to enterinformation for a new counterparty, search a list of counterparties,view and edit basic information for counterparties, view and editfinancial information for counterparties, view and edit notes regardingto counterparties, view and edit a limits of counterparties, viewposition versus limit information for counterparties, view the currentday's position information for counterparties, and view cumulativeposition information for counterparties by selecting icons 301, 302,303, 304, 306, 307, 308, 309, and 310, respectively. Although theinterfaces that are described below in connection with selecting theseicons are explained as being presented to operators, certain of theseinterfaces may also be presented to counterparties under appropriatecircumstances.

As mentioned above, by selecting icon 301 from menu 300, an operator canenter information for a new counterparty. As used herein, the termcounterparty may be used to define any holder of a trading accountirrespective of whether that account has sub-accounts or is asub-account of another account. Turning to FIG. 4, an interface 400 thatmay be used to edit basic information for a counterparty is illustrated.As shown, interface 400 includes information areas 402, 404, 406, 408,and 410, and buttons 412, 414, 416, 418, and 420.

Within basic information area 402, an operator may view a counterpartyidentification number 422 (which is preferably selected by creditprocessor 112), view and select a credit status 424 (which may includefrozen, active, closed, open and pending), view and enter a counterparty name 426, view and enter a short name 428, view and enter a datethat the counterparty was formed 430, view and select a country code forthe counterparty 432, view and enter a tax identification number 434 forthe counterparty, view and enter the number of branches 436 operated bythe counterparty, view and select whether the counterparty is a parententity or not 438, view and edit whether the counterparty has a parententity 440 and, if so, view and select the name of the parent entity442, and view the last date the information for the counterparty wasmodified 444 and the name of the operator that last modified theinformation 446.

If a parent entity is selected in box 440 and identified in field 442,information for that parent entity may appear in parent information area406. As shown, this information may include an identification number448, an entity classification 450, a name 452, a state 454, a country456, and a geographical region 458.

In order to enter contact information like that displayed in contactinformation area 404 of interface 400, an operator may click on contactbutton 414. Upon clicking on button 414, an interface 500 as illustratedin FIG. 5 may be presented. As shown, the operator may view and edit thecontact's first name, middle initial, last name, gender, department,title, telephone number, and position in fields 502, 504, 506, 508, 510,512, 514, and 516, respectively. The operator may also view theidentification number 518 for the contact, which is preferably assignedby the credit processor, the name 520 of the operator that last modifiedthe information for the contract, and the date and time 522 that theinformation for the contact was last modified. The operator may save theinformation for a contact by clicking save button 524. The operator mayalso disassociate a contact with a counterparty and delete the contactby pressing delete button 526. Finally, when an operator is done usinginterface 400, the operator may close the interface by clicking on closebutton 528.

Although not illustrated in a figure, an operator may use a similarinterface to interface 500 to enter and edit the address informationthat is displayed in address information area 408 for a counterparty byinitially clicking on address button 416 in interface 400.

In order to enter and edit the description information that is displayedin description information area 410, an operator may click on descriptorbutton 418. Upon clicking on this button, the operator may be presentedwith an interface 600 as illustrated in FIG. 6. Within area 602 ofinterface 600, the operator may then select a descriptor type 604 thatthe operator wants to identify by clicking on the descriptor type. Asshown, descriptor types may include classification, trading philosophy,structure of firm, main product, and membership. Once the operator hasselected the descriptor type 604, a menu 606 of descriptors for thatdescriptor type may then be presented. For example, if the operatorselects the membership descriptor type, menu 606 may includedescriptors: NASD, MSRV, NYSE, ASE, CBOT, CME, AMEX, and LIFFE. If theoperator selects the classification descriptor type, menu 606 mayinclude descriptors: dealer, muni-dealer, broker-dealer, and customer.If the operator selects the trading philosophy descriptor type, menu 606may include descriptors hedge fund and commercial bank. If the operatorselects the structure-of-firm descriptor type, menu 606 may includedescriptors: corporation, general partnership, chapter-S corporation,and limited liability partnership. If the operator selects the mainproduct descriptor type, menu 606 may include descriptors: bonds, FX,IRO/IRS, and Repos. Obviously, certain descriptor types (which may beindicated by special coloring or in any other suitable manner), such asmembership, may permit multiple descriptors to be selected, and othersmay only permit one descriptor to be selected. Multiple descriptor typesmay be defined for each counterparty.

When descriptor(s) 606 are selected for a descriptor type 604, theselections may then be displayed in a list of current descriptors area608. In order to enable an operator to change the list of currentdescriptors, the operator may highlight a descriptor type and descriptorin list 608, and click remove button 610 or clear button 612. Removebutton 610 preferably removes the descriptor type and descriptor fromthe list entirely, and clear button 612 preferably allows the operatorto reenter the selections in area 602. Once the operator is done withinterface 600, the operator may click on save button 614 to save theselections and/or close button 616 to close interface 600.

After an operator has completed using interface 400, the operator mayclick on save button 412 to save the selections and/or close button 420to close interface 400.

In order to search for and view counterparty information that hasalready been entered, an operator may click on search list icon 302 inmain menu 300. After clicking on icon 302, select counterpartyinterfaces 700 and 800 may be presented as illustrated in FIGS. 7 and 8.As shown in FIG. 7, select counterparty interface 700 is shown with acounterparty list view option 702 selected. When in this view,counterparty information is displayed in a region 704 of the interface.This information may include an identification number 726, a name 728, aclassification 730, a credit status 732, a state 734, a country 736, ageographic region 738, a type 740 (e.g., parent or legal entity), acountry code 742, and a parent name 744 for the counterparty. Parentcounterparties may be displayed in one color while non-parentcounterparties may be displayed in another color.

The operator may scroll the list of information using scroll bar 746.The operator may also sort the information in the list by identificationnumber 726, name 728, classification 730, credit status 732, state 734,country 736, geographic region 738, type 740, country code 742, andparent name 744 by selecting headings 706, 708, 710, 712, 714, 716, 718,720, 722, and 724, respectively. Repeatedly selecting the same headingmay toggle the order of the sort from ascending to descending and viceversa.

The operator may also restrict the items included in the list in region704 by entering characters in one of fields 748 corresponding toidentification number 726, name 728, classification 730, credit status732, state 734, country 736, geographic region 738, type 740, countrycode 742, and parent name 744 and pressing retrieve button 750. Forexample, the letters “RE” have been entered in the one of fields 748corresponding to name 728. Accordingly, only counterparties with namesbeginning with the letters “RE” are included in the list. The number ofcounterparties that are in the list may be indicated by row count field752.

The operator may double click on any row in the list in order toactivate interface 400 with that counterparty's information presented.The operator may also select a counterparty by clicking on a row so thata highlight region 754 appears in the row, and then clear thecounterparty's information from the list by clicking on clear button 756or select to activate interface 400 with that counterparty's informationpresented by clicking on select button 758. The operator may closeinterface 700 by clicking close button 760.

FIG. 8 illustrates select counterparty interface 800 with a parent treeview option 802 selected. Interface 800 may include three viewingwindows 804, 806, and 808. In window 804, a parent tree view list may bepresented. The list may include a list of counterparties,sub-counterparties of those counterparties, sub-sub-counterparties ofthe sub-counterparties, and so on. As illustrated, a plus sign 810 maybe used to indicate a counterparty that has a sub-counterparty. In thecase of “Republic Holdings”, its sub-counterparty's identificationnumber and name may be indicated by clicking on plus sign 810. Once thishas been done, the plus sign may change to a minus sign 812 and thesub-counterparty's information may be indicated. In the case of “ReadyEnterprises”, its sub-counterparty is “Ready Trade”. In the instance ofcounterparties where no sub-counterparty exists, these counterpartiesmay be indicated without either a plus sign 810 or a minus sign 812 toindicate this status.

Once an operator has clicked on a counterparty in window 804, thesub-counterparties for that counterparty may also be listed in legalentity list window 806. At the same time, additional information for theclicked-on counterparty may be displayed in window 808. This additionalinformation may include basic counterparty information 814, financialstatement information 816, and parent information 818 (if applicable).

The operator may double click on any counterparty in the lists ofwindows 804 and 806 in order to activate interface 400 with thatcounterparty's information presented. The operator may also select acounterparty by clicking on that counterparty in the lists of windows804 and 806 and click on select button 820 in order to activateinterface 400 with that counterparty's information presented. Theoperator may close interface 800 by clicking close button 822.

Referring back to FIG. 3, selecting basic information icon 303 from mainmenu 300 may present interface 400 with the information for thecounterparty that was last displayed in the interface. As explainedabove, the operator may then view and edit the information displayed.

From main menu 300, an operator may also select to view, enter, and editfinancial statements for the last selected counterparty by clicking onfinancial information icon button 304. In response, financial statementsinterface 900 may be presented as illustrated in FIG. 9. As shown,interface 900 may contain a statement list 902 and a statement detail904 for a selected statement in list 902. By clicking on a statement 906so that the statement becomes highlighted, a corresponding statementdetail 904 may be presented.

In order to modify the contents of a financial statement 906, theoperator may click modify button 910. As shown in FIG. 10, upon clickingbutton 910, interface 1000 may be presented. Through interface 1000, theoperator may edit the values in fields 1002, view the previous statementdetails in region 1004 if available (none shown), set the status 1006for the financial statement (e.g., audited or unaudited), set thecurrency 1008 for the financial statement, and set the date 1010 for thefinancial statement (although, preferably the date cannot be alteredonce set). After the operator is satisfied with the settings ininterface 1000, the operator may save the settings by clicking on savebutton 1012 and then close interface 1000 by clicking on close button1014.

Similarly, from interface 900, an operator can create a new financialstatement by clicking new button 912 and enter the pertinent informationin interface 1000 of FIG. 10. By clicking on print button 914, anoperator can print a financial statement. By clicking on save button908, an operator can save one or more new financial statements ormodifications to one or more financial statements. Finally, by clickingon close button 916, an operator can close interface 900.

If the operator clicks on note icon 306 from main menu 300, a noteinformation interface 1100 may be presented as illustrated in FIG. 11.As shown, interface 1100 includes a note type list 1102 and a notes area1104. Note type list 1102 includes various types of notes that may beentered and displayed. Upon selecting a note type, such as note type1110, notes area 1104 may display the corresponding notes 1108 for theselected type. Notes area 1104 may also present author information 1106for the note which may include a note identification number, an operatorname, and a date and time the note was created or modified. In order toshow notes for all note types in list 1102, the operator may click onshow all box 1112.

To create a new note type for list 1102, the operator may click oncreate new type box 1114. Upon doing so, a dialog box may appearprompting the operator to enter a name for the new note type. Onceentered, the note type will preferably appear in list 1102. In order todelete a note type, the operator may select a note type in list 1102 andclick on delete type button 1116. Ail notes related to that type maythen be deleted, the user may be prompted whether each note is to bedeleted or converted to another note type, or all notes may be convertedto another note type.

By clicking on new button 1122, an operator may create a new note of thetype selected. By clicking on delete button 1120, an operator may deletea selected note. By clicking on refresh button 1124, an operator canrefresh the notes displayed in interface 1100. This may be particularlyuseful where more than one operator is entering notes for a givencounterparty. By clicking on save button 1118, an operator can savenewly created notes and modifications to notes. Finally, by clicking onclose button 1126, an operator can close interface 1100.

An operator may view credit limits for one or more counterparty accountsby clicking on limit list icon 307 in main menu 300 of FIG. 3. As shownin FIG. 12, an interface 1200 may then be displayed. Interface 1200 mayinclude a subcategory list 1202 showing various trading markets in thetrading system and a limit list 1204 showing credit limits for certaincounterparty accounts. Subcategory list 1202 may be used to selecttrading markets in the trading system for which the operator would liketo view trading limits in list 1204. As shown, all subcategories may beselected in list 1202. This may be accomplished by selecting radiobutton 1208. To unselect all subcategories, the operator may selectradio button 1210. The operator may also restrict the counterpartieslisted in list 1204 by entering a name or a portion of a name in field1212. To update the counterparty accounts shown in list 1204, retrievebutton 1214 may be clicked. Row count 1218 may show the number ofcounterparty accounts listed in list 1204.

As shown, limit list 1204 may indicate a counterparty number for eachaccount, a counterparty name for each account, a limit subcategory foreach account, a limit type for each account, whether each account hasbeen shut off, whether each account has reached its limit, the LBE netlimit, the LBE gross limit, the principal net limit, the principal grosslimit, the VAR net limit, the VAR gross limit, the MTM net limit, theMTM gross limit, and any other suitable information. In order to updatethis information, an operator may click on update mode box 1220 andenter the desired changes in list 1204.

To view the account limits for a particular counterparty, the operatormay select the counterparty from list 1204 and then click on accountlimit button 1224. In response, account limit list interface 1300 may bepresented. Interface 1300 may list all account level limits for acounterparty in list 1302, the counterparty level limits for thecounterparty in region 1304, and accounts which do not have their ownlimits and which are therefore subject to the counterparty level limitsfor the counterparty. An operator may update the limits indicated foraccounts in list 1302 by clicking on update mode box 1308 and changingthe values in the fields of list 1302.

A new account limit may be added to list 1302 by clicking on new button1312, or an existing account limit may be modified by clicking on modifybutton 1311. After an operator clicks on button 1312 or 1311, a limitentry interface 1400 may be presented as illustrated in FIG. 14. Byselecting and modifying the various fields 1402, the operator may theset the account limits and other parameters to the desired settings. Theoperator may then save the new settings by clicking on save button 1404.The operator may close interface 1400 by clicking on close button 1406.

By clicking on button 1314, the operator may refresh the informationdisplayed in interface 1300. By clicking on print button 1316, theoperator may print out the information displayed in interface 1300. Byclicking on export button, 1318, the operator may export the informationdisplayed in interface 1300 to a data file. By clicking on save button1310, the operator may save an changes or additions made to the limitsor other parameters displayed in interface 1300. Finally, by clicking onclose button 1320, the operator may close interface 1300.

Turning back to interface 1200 of FIG. 12, as illustrated, interface1200 may also include a counterparty-without-limit list 1206 showingcounterparties for which no limits have been set for the selectedtrading markets. These counterparties may not be eligible to trade inthose trading markets because no limits have been set.Counterparty-without-limit list 1206 may be displayed by clicking oncounterparty-without-limit box 1216.

By clicking on print button 1226, the operator may print out theinformation in interface 1200. By clicking on export button 1228, theoperator may export the information in interface 1200 to a data file. Byclicking on save button 1222, the operator may save any additions ormodifications to the information displayed in interface 1200. Finally,by clicking close button 1230, the operator may close interface 1200.

In order to view position versus limit information for one or morecounterparties in one or more trading markets of the trading system, anoperator may click on position versus limit icon 308 of main menu 300 ofFIG. 3. Upon selecting icon 308, position versus limit interface 1500 ofFIG. 15 may be displayed. Interface 1500 may include a list 1502 oftrade information for each counterparty corresponding to a category andone or more subcategories selected in fields 1504 and 1506,respectively. By clicking on radio buttons 1508 and 1510 and thenclicking on retrieve button 1512, the operator may respectively selectand unselect all of the categories and subcategories in fields 1504 and1506 and then view the results in list 1502. The values in list 1502 maythen be updated either manually or automatically by selecting one of theradio buttons in refresh settings 1514.

As shown in interface 1500, list 1502 may include for each counterpartya counterparty identification number, a counterparty name, a limit type,a new limit type, a limit subcategory, whether the counterparty has beenshut off, the percentage of the limit for initial warning, the quantityof trades executed, the LBE net position, the LBE net limit, and thepercentage of the LBE net limit reached so far.

As with all position related interfaces and limit related interfaces,the information presented may be presented in white when thecounterparty's accounts are in good standing, in yellow when theaccounts are over their warning limits, and in red when the accounts areover their credit limit?

To view position versus limit information for all of a particularcounterparty's accounts in a particular subcategory, an operator mayselect a set of counterparty accounts in the selected subcategory inlist 1502 and then click on account button 1516. Upon clicking onaccount button 1516, position versus account detail interface 1600 maybe presented as shown in FIG. 16. As illustrated, this interface mayinclude a list of accounts 1602 for the selected counterparty andsubcategory 1601. This list may indicate for each account the accountnumber, the account name, the active status, the shut off status, thewarning limit percentage, the quantity of trades so far, the LBE netposition, the LBE net limit, the percentage of the LBE net limit, theLBE gross position, and the LBE gross limit. The operator may closeinterface 1600 by clicking on close button 1604.

To view position versus limit information for all transactions in aparticular subcategory for a particular counterparty, an operator mayselect a set of counterparty accounts in the selected subcategory inlist 1502 and then click on transaction button 1518. Upon clicking ontransaction button 1518, position versus limit interface 1700 may bepresented as shown in FIG. 17. As illustrated, this interface mayinclude a list of transactions in a selected subcategory 1704 for aselected counterparty. For each transaction, this list may indicateparticulars of the transaction including the quantity, the LBE, theprincipal, the price, and whether the transaction was a buy or sell. Byclicking on close button 1706, the operator may close interface 1700.

Referring back to FIG. 15, once the operator is done using interface1500, the operator may close the interface by clicking on close button1520.

In order to view position information for the current trading day, anoperator may click on today's position icon 309 from main menu 300 ofFIG. 3. As shown in FIG. 18, an interface 1800 may then be presented.Upon selecting a category and one or more subcategories in fields 1804and 1806, the operator may view a list of position information for eachcounterparty participating in the trading markets corresponding to theselected category and subcategories. This information may include thecounterparty identification number, the counterparty name, thesubcategory, the quantity, LBE net position, the LBE gross position, theLBE long position, the LBE short position, etc. To view positioninformation for each of a counterparty's accounts in a selectedsubcategory, an operator may select the desired counterparty andcategory in list 1802 and click on account button 1808. Upon clicking onbutton 1808 a list 1902 showing the current trading day's positioninformation for the corresponding accounts may be presented in aninterface 1900. Each of interfaces 1800 and 1900 may be closed bypressing close buttons 1810 and 1904.

In order to view cumulative position information, an operator may clickon cumulative position icon 310 from main menu 300 of FIG. 3. As shownin FIG. 20, an interface 2000 may then be presented. Upon selecting acategory and one or more subcategories in fields 2004 and 2006, theoperator may view a list of cumulative position information for eachcounterparty participating in the trading markets corresponding to theselected category and subcategories. This information may include thecounterparty identification number, the counterparty name, thesubcategory, the quantity, LBE net position, the LBE gross position, theLBE long position, the LBE short position, etc. To view cumulativeposition information for each of a counterparty's accounts in a selectedsubcategory, an operator may select the desired counterparty andcategory in list 2002 and click on account button 2008. Upon clicking onbutton 2008 a list 2102 showing the cumulative position information forthe corresponding accounts may be presented in an interface 2100. Eachof interfaces 2000 and 2100 may be closed by pressing close buttons 2010and 2104.

Those skilled in the art will appreciate that the present invention canbe practiced by other than the described embodiments, which arepresented for purposes of illustration and not of limitation, and thepresent invention is limited only by the claims which follow.

What is claimed is:
 1. A method for monitoring credit of a counterpartyhaving a parent entity, comprising: receiving trade information relatingto trades entered into by the counterparty; accumulating positions forthe counterparty indicated by the trade information with previouslyaccumulated positions; accumulating positions for the parent entityindicated by the trade information with previously accumulatedpositions; comparing at least one of accumulated counterparty positionsand accumulated parent entity positions with at least one trading limit;and shutting off trading for the counterparty when at least one of theaccumulated counterparty positions and the accumulated parent entitypositions exceeds the at least one trading limit.
 2. The method of claim1, further comprising: receiving trade information relating to at leastone of cleared trades and failed trades; adjusting accumulatedcounterparty positions based upon the trade information relating to theat least one of the cleared trades and the failed trades; and adjustingaccumulated parent entity positions based upon the trade informationrelating to the at least one of the cleared trades and the failedtrades.
 3. The method of claim 1, further comprising accumulatingcounter party positions based upon long-bond-equivalents.
 4. The methodof claim 1, further comprising accumulating parent entity positionsbased upon long-bond-equivalents.
 5. The method of claim 1, furthercomprising updating an operator interface that shows the accumulatedcounterparty positions.
 6. The method of claim 1, further comprisingupdating an operator interface that shows the accumulated parent entitypositions.
 7. The method of claim 1, wherein the comparing of at leastone of accumulated counterparty positions and accumulated parent entitypositions with at least one trading limit comprising: determiningwhether the at least one trading limit includes a limit for theaccumulated counterparty positions; and comparing the accumulatedcounterparty positions to the limit for the accumulated counterpartypositions when the limit exists.
 8. The method of claim 1, wherein thecomparing of at least one of accumulated counterparty positions andaccumulated parent entity positions with at least one trading limitcomprising: determining whether the at least one trading limit includesa limit for the accumulated parent entity positions; and comparing theaccumulated parent entity positions to the limit for the accumulatedparent entity positions when the limit exists.
 9. The method of claim 1,further comprising sending a message to indicate when trading for thecounterparty has been shut off.
 10. The method of claim 1, furthercomprising: comparing at least one of accumulated counterparty positionsand accumulated parent entity positions with at least one tradingwarning level; and sending a message to indicate when at least one ofthe accumulated counterparty positions and the accumulated parent entitypositions exceeds the at least one trading warning level.
 11. The methodof claim 1, further comprising providing an operator interface thatprompts an operator to specify the at least one trading limit.
 12. Asystem for monitoring credit of a counterparty having a parent entity,comprising: a trading system the provides trade information relating totrades entered into by the counterparty; and a credit processor that:receives the trade information relating to the trades entered into bythe counterparty, accumulates positions for the counterparty indicatedby the trade information with previously accumulated positions,accumulates positions for the parent entity indicated by the tradeinformation with previously accumulated positions, compares at least oneof accumulated counterparty positions and accumulated parent entitypositions with at least one trading limit; and shuts off trading for thecounterparty when at least one of the accumulated counterparty positionsand the accumulated parent entity positions exceeds the at least onetrading limit.
 13. The system of claim 12, further comprising a clearingsystem that provides trade information relating to at least one ofcleared trades and failed trades, wherein the credit processor alsoreceives trade information relating to at least one of cleared tradesand failed trades, adjusts accumulated counterparty positions based uponthe trade information relating to the at least one of the cleared tradesand the failed trades, and adjusts accumulated parent entity positionsbased upon the trade information relating to the at least one of thecleared trades and the failed trades.
 14. The system of claim 12,wherein the credit processor also accumulates counter party positionsbased upon long-bond-equivalents.
 15. The system of claim 12, whereinthe credit processor also accumulates parent entity positions based uponlong-bond-equivalents.
 16. The system of claim 12, wherein the creditprocessor also updates an operator interface that shows the accumulatedcounterparty positions.
 17. The system of claim 12, wherein the creditprocessor also updates an operator interface that shows the accumulatedparent entity positions.
 18. The system of claim 12, wherein the creditprocessor in comparing of at least one of accumulated counterpartypositions and accumulated parent entity positions with at least onetrading limit: determines whether the at least one trading limitincludes a limit for the accumulated counterparty positions; andcompares the accumulated counterparty positions to the limit for theaccumulated counterparty positions when the limit exists.
 19. The systemof claim 12, wherein the credit processor in comparing of at least oneof accumulated counterparty positions and accumulated parent entitypositions with at least one trading limit: determines whether the atleast one trading limit includes a limit for the accumulated parententity positions; and compares the accumulated parent entity positionsto the limit for the accumulated parent entity positions when the limitexists.
 20. The system of claim 12, wherein the credit processor alsosends a message to indicate when trading for the counterparty has beenshut off.
 21. The system of claim 12, wherein the credit processor also:compares at least one of accumulated counterparty positions andaccumulated parent entity positions with at least one trading warninglevel; and sends a message to indicate when at least one of theaccumulated counterparty positions and the accumulated parent entitypositions exceeds the at least one trading warning level.
 22. The systemof claim 12, wherein the credit processor also provides an operatorinterface that prompts an operator to specify the at least one tradinglimit.